Fixed tests on HHVM 

I fixed the errors on on the test suit on HHVM. They are related to HHVM and not this lib. I created workarounds and made a comment about it. 

I also fixed some failures that relied on the order of the fixers returned from `Fixer::getFixers`. When using `usort` on HHVM you can't rely on the order between objects with the same weight. 

There are still failures that I have not managed to figure out a good workaround for. They are related to the `token_get_all` function. On HHVM `token_get_all` does not return the same output. 
Example: 
``` php

$var = <<<'EOF'
<?php
$b = <<<'TEXT'
Foo TEXT;
Bar1}


FooFoo
TEXT;
EOF;

var_dump(token_get_all($var));
```
``` php
//Prints on PHP 5.5: 

array(7) {
  [0] =>
  array(3) {
    [0] =>
    int(374)
    [1] =>
    string(6) "<?php
"
    [2] =>
    int(1)
  }
  [1] =>
  array(3) {
    [0] =>
    int(310)
    [1] =>
    string(2) "$b"
    [2] =>
    int(2)
  }
  [2] =>
  array(3) {
    [0] =>
    int(377)
    [1] =>
    string(1) " "
    [2] =>
    int(2)
  }
  [3] =>
  string(1) "="
  [4] =>
  array(3) {
    [0] =>
    int(377)
    [1] =>
    string(1) " "
    [2] =>
    int(2)
  }
  [5] =>
  array(3) {
    [0] =>
    int(378)
    [1] =>
    string(10) "<<<'TEXT'
"
    [2] =>
    int(2)
  }
  [6] =>
  array(3) {
    [0] =>
    int(315)
    [1] =>
    string(30) "Foo TEXT;
Bar1}


FooFoo
TEXT;"
    [2] =>
    int(3)
  }
}

```

``` php
//Prints on HHVM:

array(6) {
  [0]=>
  array(3) {
    [0]=>
    int(368)
    [1]=>
    string(6) "<?php
"
    [2]=>
    int(1)
  }
  [1]=>
  array(3) {
    [0]=>
    int(309)
    [1]=>
    string(2) "$b"
    [2]=>
    int(2)
  }
  [2]=>
  array(3) {
    [0]=>
    int(371)
    [1]=>
    string(1) " "
    [2]=>
    int(2)
  }
  [3]=>
  string(1) "="
  [4]=>
  array(3) {
    [0]=>
    int(371)
    [1]=>
    string(1) " "
    [2]=>
    int(2)
  }
  [5]=>
  array(3) {
    [0]=>
    int(372)
    [1]=>
    string(10) "<<<'TEXT'
"
    [2]=>
    int(2)
  }
}
```
@keradus PHP explicitly documents it as an undefined behavior, which means you cannot rely on the order (they are free to change it without notice even in patch releases if they find it necessary to fix a bug in the sorting algorithm or to make it faster)