Format numeric tag values using the value of the -unit flag.
Added a testcase for this behavior.

When generating callgrind format output, produce cost lines at
instruction granularity. This allows visualizers supporting the
callgrind format to display instruction-level profiling information.

We also need to provide the object file (ob=) in order for tools to find
the object file to disassemble when displaying assembly.

We opportunistically group cost lines corressponding to the same
function together, reducing the number of superfluous description lines.
Subposition compression (relative position numbering) is also used to
reduce the output size.

Provide native Go mocks for binutils to use during testing, instead of
relying on shell-script mocks of those tools.

Also update the build instructions to use go get