I asked for benchmarks because I don't know anything about Windows virtual memory management, but if other people think this patch should go in then it's fine.

The main point of using VirtualAlloc/VirtualFree was, in my mind, to allow *releasing* memory in more cases than when relying on free() (assuming Windows uses some sbrk() equivalent). But perhaps Windows is already tuned to release memory on most free() calls.