Rails Ruby on Rails

In SQL there is the type time, that stores a given time of day without being attached to any date. Since Ruby doesn't have a class for handling only times, Active Record maps a time column to a dummy Time object, with the date always set to 2000-01-01. This is useful when we are comparing two time attributes: since the date is the same, the comparison considers only the time, making the abstraction perfect.
However, the abstraction leaks when we compare a time attribute with a Time instance from elsewhere. To make it work, the user has to manually convert it to the epoch date or compare using only seconds_since_midnight to consider only the time of day. And it's painful in both ways.
To solve this, I see three alternatives:

1. Make the user conscious of the epoch date and provide a method to_dummy_time, that transports a Time instance to 2000-01-01.
   
2. Mark the Time instances that refers to time-only and compare them ignoring the date.
   
3. Create a TimeOfDay type in Ruby to handle times properly.

Among these, I think the second makes the best compromise between transparency and code (the third implementation requires a lot of code to make it work with Date, DateTime and Time safely). In fact, I implemented it as a plugin some time ago: http://github.com/lailsonbm/time_of_day. We're using it on a Rails 3 project with success since then. The README shows the problem and describes how we handle it.
So, what do you think guys? It shouldn't be difficult to make a patch to Rails, I surely can do this.