I'm using GetProcessHeaps() and HeapWalk() to step through all the heaps in a program, counting the total allocations.
Strangely, the number of allocated bytes doesn't seem to change, even when I use new to allocate a huge data structure -- several tens of megabytes.
Is the MSVC operator new getting memory from some other location other than the heap? I'm digging around MSDN but haven't found any info yet.
I want to find a way to track allocations on the byte (not page) level, and I really don't want to go down the path of overriding global new/delete.