anchor.diff:     issue) and describe the approach and design you have in mind. Keep in mind
      that Stormpot is implemented with a very strict adherence to TDD.
      Finally, make sure to respect the existing indentation and formatting.
  +   Use `mvn checkstyle:check` to check your formatting.
      If you are writing a test that takes more than a few hundred milliseconds to
      run, then put it in the `stormpot.slow` test package; either in the existing
      `PoolIT` suite, or in a new `\*IT` suite.
  
positive.code:     object.release();
    }
  }
  --
  
  == Contributing
  
   * *Report bugs* preferably with a failing test. You can submit a pull-request
     that adds a failing test that demonstrates the behaviour you think is wrong
  
negative.code:    `open target/site/jacoco/index.html`. Get mutation test coverage with
     `mvn clean test-compile org.pitest:pitest-maven:mutationCoverage` and
     `open target/pit-reports/*/index.html`.
   * *Update* Maven plugins with `mvn versions:display-plugin-updates`, or other
     dependencies with `versions:display-dependency-updates`.
   * *Add to the ecosystem* and make Stormpot more than just an object pool.
     This is a good thing to take on if you'd like to contribute code, but you
     find the Stormpot code base itself to be intimidating (which, by the way, I
  