Profiler API - Locks, Threading.Monitor.Enter and Exit

Question

I'm using the Profiler API in a project in order to track the locks made using Monitor.Enter, Monitor.Exit, and the lock keyword. I planned to do this by outputting using a pipe, the events from the FunctionEnter3WithInfo and FunctionLeave3WithInfo callbacks.
These callbacks are called when methods are entered and exited, and appear to be functioning fine regarding their implementation - they generate a large output of methods that had been entered and left, but I'm not receiving callbacks for the following:
ENTER: Monitor.Exit
LEAVE: Monitor.Enter and Monitor.Exit
Oddly enough, I do get receive a callback for entering Monitor.Enter. Other than these problematic methods, I appear to be getting calls from the Profiler API for everything else. 
Is there a known issue regarding these methods not being reported by the API? 
Alternatively, if there's a better way of achieving my goal than the way I'm doing it, feel free to point me in the right direction :)
Thanks,
Olu

Answer 1

Thanks for the reply Brian,
I don't get a JITInlining callback for Monitor.Exit (however I do for some Monitor.Enter calls). For FunctionTailcall3WithInfo, I also don't get a callback for Monitor.Exit (but I do for some Monitor.Enter calls).
I'm not getting anything from ExceptionUnwindFunctionEnter, though when manually tested by throwing an exception within a try-catch, I get a callback.
If it helps, I have the following flags set for events:
COR_PRF_MONITOR_ALL
COR_PRF_ENABLE_FUNCTION_ARGS
COR_PRF_ENABLE_FUNCTION_RETVAL
COR_PRF_ENABLE_FRAME_INFO
Additionally, I've tried the following flags to see if it resolves the issue:
COR_PRF_DISABLE_INLINING
COR_PRF_DISABLE_OPTIMIZATIONS
Edit 1: Using COR_PRF_DISABLE_OPTIMIZATIONS now means I get a callback to FunctionLeave3WithInfo when Monitor.Enter leaves, however there is still no sign of Monitor.Exit
Edit 2: As a test, in the small application that I'm profiling, I've wrapped the Monitor.Exit and Monitor.Enter method calls in another class, so I can call them as so:
CCMonitor.Enter(obj) and CCMonitor.Exit(obj).
The profiler reports both the enter and leave of these functions correctly.
Thanks,
Olu