Had a report of a memory leak in an application, have been trying to verify the leak but unfortunately I am hitting a bit of a road block. The application does have some win32 calls, and in the past, I've used the profiler to help determine if some of my DLLs which were being marshalled had a leak in them. I now am noticing (perhaps this has always been there?) that taking a snapshot seems to raise the unmanaged allocation. To test this, I created a blank windows form and then profiled it. If I take snapshots fairly close together, the unmanaged allocation starts rising pretty quickly. If i leave it sit there for hours, it stays exactly the same. Is this expected? If so, is there a reliable way to use this product to test more than managed memory leaks? I do understand the product can't profile my instances, calls, etc. in the win32 calls, and i'm ok with this, but it would be nice to be able to tell, at a glance, if the unmanaged allocation was rising continuously with the utility. This way I could at least confirm/deny whether or not the win32 calls are leaking at all.