Version 1.0.1pre1
Fix use of @cache in place of @__cache__

This is an error from pre-version-control days, or at least that's what
git-blame tells me.
Fix enormously stupid Memory#copy! error

Was adding the destination offset to the source pointer for copies.

For all the crap I do to make sure things like this don't happen, it's
hard to prevent 3am typos.
Fix bracing on sd_check_null_block.
Add a bounds-checking function for the get_* functions.
Add bounds checks to get_* functions via sd_check_block_bounds.
Fix copy for struct type setters.
Unravel get/set functions a bit so they're not mostly one-liners.

The reason for this is sort of two-fold:

1. I don't like lines extending too far beyond 80 columns. It doesn't
   look very nice and makes it difficult to read the code.

2. The lines were already difficult to read, so I want to break them up
   into more digestible chunks. This means more lines, but it also means
   it's easier to debug and easier to see what's going on.

The code is basically the same, it's just spread out a bit more so it's
not one giant block of pointer magic.
Move block bytesize grab into sd_check_block_bounds.

This does mean I can't throw any old block_size into the bounds check,
but it does keep it tied to a specific block and therefore sort of kind
of ensures that the block is the real deal.
Replace all use of FIX2* with NUM2*.

This is slightly slower for converting values to something in C, the
upside is that it doesn't produce an error if the number isn't a Fixnum.
This will still produce errors if you try to write a signed integer that
exceeds the maximum (or minimum, I suppose -- that seems to be a less
common problem) possible value of an int, though.
Correct the to_s documentation to mention that nil is an implicit true.

If that doesn't make sense to you, don't worry, it doesn't make sense to
me either.
Alias malloc as __malloc__.

Reason for this is that someone might want to override malloc and
although that's a bad idea and should never be done, it is possible and
probably relatively safe within the confines of only what snow-data
does with malloc.

I'll convert all snow-data calls to malloc to __malloc__ to sort of
guard them against overrides where possible.
Replace all malloc calls with __malloc__.

See previous commit about aliasing malloc to __malloc__ just in case
someone really, really wants to override it.
Add note about subclassing Memory, __wrap__, and __malloc__.
Bounds-checking note in README.

Now that every op does this check and raises an exception for it in most
cases, I think I can remove that note.
Add a brief example to the README.

This just shows how to define a vertex type. Unfortunately, the amount
of boilerplate necessary to get a full GL example up and running makes
it prohibitive for an in-README sample, but this should suffice to at
least show how snow-data might be used.
Update summary and description.
Version 1.0.0

I'll consider this the actual release for now.

Bounds-checks ahoy!