Ok, seems the memory checking code is sadly unreliable.

.
Even the OS X activity monitor sometimes shows totally silly results for virtual memory use sometime (16 Exabytes for a 32-Bit process???), so probably the OS X/mach API for this is just crap. Will see if some smoothing function (e.g. take the average of the last 30 seconds) is more reliable.
Kathrine