Timeuuid support for range queries

When doing range queries on Timeuuid columns, we should allow `Time`-like values and use the `minTimeuuid()` and `maxTimeuuid()` CQL functions described [here](http://www.datastax.com/documentation/cql/3.0/webhelp/index.html#cql/cql_reference/cql_data_types_c.html#reference_ds_axc_xk5_yj).

Given the following:

>   The min/maxTimeuuid example selects all rows where the timeuuid column, t, is strictly later than 2013-01-01 00:05+0000 but strictly earlier than 2013-02-02 10:00+0000. The t >= maxTimeuuid('2013-01-01 00:05+0000') does not select a timeuuid generated exactly at 2013-01-01 00:05+0000 and is essentially equivalent to t > maxTimeuuid('2013-01-01 00:05+0000').

We should pass the UUIDs as integer literals containing the millisecond epoch timestamp, and I *think* we should just subtract one millisecond and swap `minTimeuuid`/`maxTimeuuid` if it's an inclusive range (or we could just disallow inclusive ranges for time inputs to timeuuid ranges).