add metrics for ExecutorService and ThreadFactory
'wrappee' sounds silly, renaming
add javadocs for java.util.concurrent instrumentations
implement ExecutionService instead of inheriting from AbstractExecutionService
rename underlying implementations as 'delegate'
use MetricRegistry#name instead of doing concatenation manually
use a Meter for completed tasks
make Metric members private and retrieve them from the registry for testing
format to adhere to project code convention
mark fields as final, removed a stdout statement
use meters for 'created' and 'finished'/'terminated' metrics
have both test classes terminate the generated threads cleanly
[maven-release-plugin] prepare for next development iteration
Update relnotes.
Bump doc version.
InstrumentedHandler: Remove duplicate calls to requests.update(...)

The timer is updated inside updateResponses(). This causes the count of this
timer to be double what it should be, and probably biased the times for the
exponentially decaying reservoirs.

Commit 33113e55cb fixed this same bug for activeRequests.
New metric 'utilization-max' to track thread usage out of max pool size
MeterSerializer.serialize had m1_rate and m15_rate transposed

There was a simple problem, where the MeterSerializer has the wrong
labels for m1_rate and m15_rate.
Updated Test Case for the MetricsModule meter serializer
loosen type requirements for JmxAttributeGauge constructor

Previously an MBeanServer was required to create a JmxAttributeGauge object
even though instances of JmxAttributeGauge only use methods from the
MBeanServer's super-interface, MBeanServerConnection. Relaxing this constraint
allows passing a JmxAttributeGauge any MBeanServerConnection (e.g. the
connection returned by JMXConnector.getMBeanServerConnection).