Update: I ran valgrind. Here's the summary:
==13647== LEAK SUMMARY:
==13647== definitely lost: 274,913 bytes in 62 blocks
==13647== indirectly lost: 29,937 bytes in 1,264 blocks
==13647== possibly lost: 71,528 bytes in 876 blocks
==13647== still reachable: 70,136,419 bytes in 31,730 blocks
==13647== suppressed: 0 bytes in 0 blocks
==13647== Reachable blocks (those to which a pointer was found) are not
shown.
==13647== To see them, rerun with: --leak-check=full --show-leak-kinds=all
Looks like there definitely is a memory leak which leaks sizable chunks
of memory (not just a KB or two).
GI
--
The system requirements said 'Requires Windows 95 or better', so I
bought a Mac.
