Andrea,

GG analyzed the val.log you created (https://www.dropbox.com/s/rj0b0mhuyvg1kjl/val.log?dl=0)

Indeed it looks good.  He did check in 1 change where some memory was leaking so the line from the log that reads: "611,536 (296 direct, 611,240 indirect) bytes in 1 blocks are definitely lost" should be gone the next time you run valgrind. 

If you get the chance to run again, this time could you do a little "grouping" so this new code is checked to make sure it is not leaking memory?  Thanks, I do not know how you have the patience to run Valgrind as I do not!  GG/Phyllis