An interesting article on exception handling, also with respect to handling corrupted state exceptions:
CLR Inside Out: Handling Corrupted State Exceptions
However, I would assume that there is something wrong either in the way you are calling the native method or in the native method itself. It's best to fix the original problem that is causing the CSE instead of catching exceptions that indicate that your application is no longer in a stable state. You probably will only make things worse by catching such an expcetion. The article mentioned above states:
Even though the CLR prevents you from naively catching CSEs, it's still not a good idea to catch overly broad classes of exceptions. But catch (Exception e) appears in a lot of code, and it's unlikely that this will change. By not delivering exceptions that represent a corrupted process state to code that naively catches all exceptions, you prevent this code from making a serious situation worse.