We have a mix of new/delete and malloc/free in the vpr code base. This is dangerous as someone might free something created with new, or delete something created with malloc.

Proposed Behaviour & Solution

Remove all free/malloc/calloc/realloc calls and replace with new/delete equivalents.

Take some care when dealing with the vtr_chunk_alloc routines, as we still want those efficient memory pooling allocators (if they call new/delete when they actually get the memory they're managing in chunks, that would be sufficient for this clean up).

Holding this for now and will assign to a summer student.