Fix memory leak in SOADataVector
After 39bbdcfa SOAData doesn't deallocate memory on destruction but instead that has to be done explicitly. This case seems to have been missed.
Fixes MooreOnline#8 (closed)
Edited by Rosen Matev
After 39bbdcfa SOAData doesn't deallocate memory on destruction but instead that has to be done explicitly. This case seems to have been missed.
Fixes MooreOnline#8 (closed)