New command instances

I ran into a case where having the commands clone automatically was breaking things for me and I hadn't expected it. When writing other unit tests, some environmental stuff for one command was persisting into another test.

The `new()` method doesn't really jive with the cloning mentality of clom, but I couldn't think of a better way since I think the existing implicit clone is preferred.

Tests included and everything passes.