Don't use "&&" move semantics

This was just a bad idea...  I thought I'd gotten rid of all of these!
Run tests under valgrind

This would have caught that "&&" bug I just fixed.  Luckily everything
else appears to be clean!