use map to track stat commands


- [x] Version bumped (see semver.org)
- [x] CHANGELOG updated
- [ ] README updated (optional)
- [ ] Code reviewed
- [x] [Jenkins build passes](http://build.sendgrid.net:8080/job/go-statsdclient-pullrequests/12/)


You are safe on the write operations but not on the read operations.
The Commands map is accessed directly in the tests
so those reads are not taking a lock
but, if there's no concurrent access in the tests it shouldn't theoretically be a problem.

Use a rlock and make Commands map private so you can truly avoid the issue.