Here are the classes, structs, unions and interfaces with brief descriptions:

C_ARMPIN	Template definition for teensy 3.0 style ARM pins, providing direct access to the various GPIO registers. Note that this uses the full port GPIO registers. In theory, in some way, bit-band register access -should- be faster, however I have found that something about the way gcc does register allocation results in the bit-band code being slower. It will need more fine tuning
C_ARMPIN_BITBAND	Template definition for teensy 3.0 style ARM pins using bit banding, providing direct access to the various GPIO registers. GCC does a poor job of optimizing around these accesses so they are not being used just yet
C_AVRPIN	Class definition for a Pin where we know the port registers at compile time for said pin. This allows us to make a lot of optimizations, as the inlined hi/lo methods will devolve to a single io register write/bitset
CAberLEDClass	The class for the AberLED shield. One object of this class, called AberLED, is automatically created (similar to how Serial works). Yes, all this time you've been writing C++, not C. You should put `AberLED.` before every function, so `AberLED.begin()` instead of just `begin()`
CCMinWait
CFastPin	The simplest level of Pin class. This relies on runtime functions durinig initialization to get the port/pin mask for the pin. Most of the accesses involve references to these static globals that get set up. This won't be the fastest set of pin operations, but it will provide pin level access on pretty much all arduino environments. In addition, it includes some methods to help optimize access in various ways. Namely, the versions of hi, lo, and fastset that take the port register as a passed in register variable (saving a global dereference), since these functions are aggressively inlined, that can help collapse out a lot of extraneous memory loads/dereferences
Cfontinfo
CInputPin
COutputPin
CPin
CSelectable
CTFT_ST7735