This method is intended for advanced users and must always be used carefully. To avoid leaking handle resources, always call this method inside a constrained execution region (CER), where a thread abort cannot interrupt processing. In the same way that unmatched SafeHandle.DangerousAddRef(Boolean@) calls can cause resource leaks, unmatched SafeHandle.DangerousRelease calls can cause invalid handle states to become visible to other threads. Do not expose SafeHandle.DangerousAddRef(Boolean@) or SafeHandle.DangerousRelease calls to untrusted code.