Remove yesterdays paging system. It can't be made to be efficient with Azure.
Alternative paging interface, using a token system.

Hm, one issue here is that this means passing the TableContinuationToken value from Azure to the user, and it's not clear if this would reveal something that should be left private. (The offset system is simpler but not supported by Azure tables)
Sample implementation for the in-memory key/value store
Add a test for the paging enumeration
Change the paging test so that it regenerates the enumeration each time (an important requirement of the paging system)
Start work on a page object for the Azure table store, change to using a task-based mechanism for retrieving the contents
Initial implementation of the Azure segmented page
Add some trace messages when KV store commits process a lot of records or take a long time