There are 2 things here that don't agree with each other. First quoted text says its OK to slop memory around and rely on ExitProcess to clean up the mess, the second is saying that a badly implemented memory allocation plan will end up thrashing the hard disk that stores the swap file.
There is a solution, write reliable code and clean up on the fly so you don't leave a mess all over the place. The operating system memory allocation strategies all come with their de-allocation procedures so its not as if the OS was designed to leave allocated memory when its no longer used.
There are simple scenarios that make the point, in Win32 you have limited memory, keep allocating 1 gig blocks and see why it fails when previous blocks are left un-allocated. Same effect in Win64 but it takes longer as there is usually more available memory. If a linked list/allocation strategy produces a disk thrashing result, change the design so it no longer doing so.
Unreliable sloppy code will come back and bite you on the arse many times with the OS saying less than nice things about you level of programming competence and shutting your app down.