Introduced the RKTableController component for iOS.

RKTableController provides a flexible, integrated system for driving iOS table views using
the RestKit object mapping engine. Local domain objects can be mapped into table cells within a
collection or presented for editing as part of a form. There are three flavors of table controllers
available:

* Static Tables: RKTableController can be used to render simple static tables that are composed of RKTableItems
presented in RKTableSections. Table items can quickly be built and added to a table without a backing model
or can have content object mapped into them for presentation.
* Network Tables: RKTableController can also render a table with the results of a network load. The typical use
case here is to have RestKit retrieve a JSON/XML payload from your remote system and then render the content into
a table.
* Core Data Tables: RKFetchedResultsTableController can efficiently drive a table view using objects pulled from a
Core Data managed object context. Typical use-cases here are for the presentation of large collections that are
pulled from a remote system, offering offline access, or speeding up a UI by using Core Data as a fast local cache.

RKTableController supports a number of bells and whistles including integrated searching/filtering and pull to refresh.

Code/ObjectMapping/RKObjectMappingProvider.h

@@ -61,7 +61,13 @@ typedef enum {
  
  @return A new autoreleased object mapping provider instance.
  */
-+ (RKObjectMappingProvider *)mappingProvider;
++ (id)mappingProvider;
+
+/**
+ Instantiate and return a new auto-released object mapping provider after
+ yielding it to the specified block for configuration
+ */
++ (id)mappingProviderUsingBlock:(void (^)(RKObjectMappingProvider *))block;
 
 /**
  Configures the mapping provider to use the RKObjectMapping or RKDynamicObjectMapping provided when