Memory leaks in capstone tests

[bobpaw]

There are memory leaks in the capCyl, capCube, and capWing tests. I think most of them are confined to the capstone library. There is one that might be associated with MeshCAP::end() not correctly destroying the iterator. Since it uses SmartMeshIterator, the free should be handled when all other iterators go out of scope.

valgrind --leak-check=full --show-kinds=all capCyl output: valgrind_capcyl.txt