Expand reporters and take suppress option in use

Would fix #21
Hmm, sorry I don't get it correctly.

But first - are you npm `2.x.x` because this is what I got with `$ npm test` on the latest npm.

```
stefan @ stefan-mac: ~/sites/grunt-jsinspect master ヾ(⌐■_■)ノ
> npm test                                                                                [19:25:30]

> grunt-jsinspect@0.3.0 test /Users/stefan/Sites/grunt-jsinspect
> grunt -- test

Running "jshint:all" (jshint) task
>> 3 files lint free.

Running "clean:tests" (clean) task
>> 0 paths cleaned.

Running "jsinspect:test" (jsinspect) task

Match - 2 instances
test/fixtures/one-duplicate.js:1,3
test/fixtures/one-duplicate.js:4,6

- test/fixtures/one-duplicate.js:1,3
+ test/fixtures/one-duplicate.js:4,6
+  var doingTwice = function () {
-  var doingOnce = function () {
     return 1 + 1;
   };

 1 match found across 1 file

Running "nodeunit:tests" (nodeunit) task
Testing jsinspect_test.js......OK
>> 5 assertions passed (136ms)

Done, without errors.
```

It is executing the grunt `test` command correctly.
In case you're not on npm 2 [this](http://4waisenkinder.de/blog/2014/10/18/npm-2-dot-0-and-the-much-better-star-npm-run-star-command/) might help.

I see, that travis hasn't have installed the latest npm by default. Changing travis.yml should do it. :)

```
language: node_js
node_js:
  - "0.10"
  - "0.11"

before_script:
  - npm install -g npm

branches:
  only:
    - master
```

I'd personally prefer to stick to grunt in this case. Because it's combining several tools we use - JSHINT, nodeunit, etc...

Let's discuss.

And another sidenote - npm is putting all binaries into `node_modules/.bin/` so there is also no need to use the binary in the dependency itself. :)