Using CHMv8

Using ConcurrentHashMapV8 since ClosedHashTable may insert a duplicate key under load and immediate closeDeletion calls.
With ConcurrentHashMapV8 being a bucket based Map the memory footprint, gc costs are to be increased slightly.
The release drops the use of the ArrayAllocator as achieving proper concurrent correctness would require extra locks.