WIP: ENH: avoid potential HashPtrTable memory leaks (#1286)

• in previous versions the HashPtrTable used a HashTable<T*> for its underlying storage and added additional routines for deallocating memory when items were deleted or the table was cleared.

  This generally works well, but direct use of any HashTable<T*> removal methods without additional wrapping results in memory leaks.

  The safer means is to use a container with its own memory management. For example, HashTable<autoPtr>.

  Any memory cleanup now becomes automatic.

added 3 commits

• cc405548 - 1 commit from branch develop
• c49c47a8 - ENH: additional HashTable emplace/insert/set methods (#1286 (closed))
• 79d915ec - WIP: ENH: avoid potential HashPtrTable memory leaks (#1286 (closed))

Compare with previous version

added 2 commits

• 7a906b7d - ENH: additional HashTable emplace/insert/set methods (#1286 (closed))
• 1910c508 - ENH: reduce risk of HashPtrTable memory leaks (#1286 (closed))

Compare with previous version

added 1 commit

• 6d0c3c47 - ENH: stop potential HashPtrTable memory leaks (#1286 (closed))

Compare with previous version

added 589 commits

• 6d0c3c47...0da9ec86 - 588 commits from branch develop
• f21144ac - ENH: stop potential HashPtrTable memory leaks (#1286 (closed))

Compare with previous version

closed

The idea did not pan out properly.