DSTM Obstacle Solved

I finally managed to solve that problem. The way I went about it was similar to reference couting. I just kept a counter of the number of objects referencing each transaction, and whenever that number would reach zero AND the transaction would be committed or aborted all the memory used by it would be freed.

There are no issues in terms of contention since each transaction is associated with only one thread.

The next step would be to find a proper memory leak tester and perform such a test. The one with Visual Studio isn't working properly for some reason (keeps crashing)!