Experiment wth using Archive::Extract to unpack dists using /bin/tar

Using the binary seems to work better than Archive::Tar, which also
leaks a lot of memory.
Remove leak detection code.  The offender is Tar::Archive!
Experiment with using Archive::Extract to unpack archives for Dist::Metadata.

Otherwise, D::M uses Archive::Tar to read the archives from memory, which
consumes a huge amount of data.
Always prefer bin tools
Tie Archive::Extract::DEBUG to PINTO_DEBUG.
Protect against blow-ups in Archive::Extract.
Better batching.
Report current time at each batch.
Display batch size in diagnostic message.
Remove xtra parens.
Add leak tracing again.
Fix syntax error.
Fix batch_count splicing.
More splicing bugs.
Tweak diagnostic messages.
Trying to diagnose and fix memory leaks.

They only happen when there is an excpetion.
The Result can contain any type of exception (string, object, whatever).

I'm not really happy with this, but it will do for now.  I would
prefer to have Pinto produce a uniform type of exception, but I'm
not really sure how to convert other types whilst preserving
stack trace and other metadata properly.
Update change log.
Bump VERSION, regen README.
v0.065_06

      Switched from using Archive::Tar to Archive::Extract.  The
      latter will attempt to use tar(1) to unpack the archive,
      which works much better with older archives.  This is a bit
      slower however.  If you don't have tar(1), it falls back
      to using Archive::Tar internally.

      NB: Archive::Tar also reads the entire archive into memory,
      so that probably explains why some of you have been getting
      out-of-memory errors.  The switch to Archive::Extract should
      help alleviate that problem (as long as you have tar).