maximum number of managed MemPools

[Sam Preston]

Currently a 64-bit bitmap (BitMap64 in types) is used to flag managed memory as used or unused. This means that there's a maximum of 64 MemPools that can be allocated. Since we're using managed memory frequently in our applications, this should be increased -- the space savings of using a bitmap structure isn't worth it anyway, so this should probably just be changed to a std::list or std::vector of booleans that can grow as necessary, and we can get rid of the BitMap32/BitMap64 types.

[Jacob Hinkle]

Fully agree

[Jacob Hinkle]

Probably the linked list is better for this.

[Jacob Hinkle]

Reviving this issue, since I think nikhil is running up against this in some large-scale 2D statistics code. We can still make it fast. I say we use a vector of bools that grows in increments of 128.

[Sam Preston]

Updated MemoryManager to use internal std::vector of mempools instead of fixed number (64) and tracking them via BitMap64. This resolves #46

→ <<cset 41b07f827008>>