Apply POD patch from https://rt.cpan.org/Public/Bug/Display.html?id=99956
POD fix

Turned C<...> into C<<...>> in places where the code contained a '>'.
Change the definition of the constant sub to potentially be more future proof

 * Don't re-enable strict in that scope, which I was doing just to be
   pedantic.

 * Make sure the variable we're inlining is only used there, and not
   later. I.e. we're basically doing something that would enable this:

    $ perl -E 'sub after { my $cp = \$_[0]; $$cp = 2 } my $value = 1; *HELLO = sub () { $value }; after($value); say HELLO(); say $value'
    1
    2

   So if FC gets his way we'd potentially not inline this sub in lieu of
   supporting changing the variable later.
Bump the Changes for 0.09
v0.09

    - Attempt to future-proof how we define the constant subs for
      possible future perl core changes, see the "Is it time to
      separate pad names from SVs?" thread on perl5-porters. No
      functional changes for currently released perls.

    - Minor POD fixes from a couple of patches sent in via RT #99956
      and pull request #1 on GitHub.