Looked into the performance issues I was having with the `G` command.
After a little profiling and then messing around with

    let start = reltime() | <do stuff> | echom reltimestr(reltime(start))

Using the `reltime` method I discovered that `grappele#Grappele()` was
running pretty quick (~60 time units). I then ran it around the

    :<c-u>call grappele#Grappele(v:count)<cr>

part of the mapping and found that it took about 130 time units.

Then doing

    nnoremap G :let start = reltime() \| execute 'normal! G' | echom reltimestr(reltime(start))

was pretty quick.

With that information, I decided to try a direct mapping bypassing the
`<Plug>` mapping just to see what that would do. Turns out the custom
`G` command works much faster with this method for some reason. In terms
of feel it's as fast as the normal `G` command.

Replacing the `<Plug>` mapping with the direct one for speed. Not really
sure what the reason for this is but I'm glad the performance is up to
snuff and actually usable now.

I'm testing this on OS X 10.8.5 with the stock Vim (7.3 (2010 Aug 15,
compiled Jun 20 2012 13:16:02)). Also noticed this issue on my Debian
server which I just found out uses the same version of Vim (7.3 (2010
Aug 15, compiled May  4 2012 04:25:35)).

* Add mapping for the recall command. Using `gG` because it's quick,
  easy to remember, and doesn't appear to be used for anything.
* Create `grappele#Recall()` function that goes to the last `G` count
* Store the most recent count passed into `G`

Using the recall command, you can `G` to the same count that you
previously used no matter what buffer you're now in.

TODO: The `G` command appears to be running slowly now for whatever
reason. Investigate what's going on.

Otherwise the mapped command is printed on the command line which isn't
necessary and adds visual noise and distraction.

Go to the end of the buffer when typed with no count, otherwise go to
the line specified by `v:count`.

Should be mapping `<Plug>Grappele` to the function call. `G` doesn't
belong in this map call. That's what the one at the end is for.

* Basic setup for the plugin:
    * `loaded` global
    * Create mapping definition based on style from tpope and System
      Copy
* Create dummy function in autoload