Measuring Rollback Usage

Is there any way to measure how much rollback is being generated by each query, and for each how much of that rollback is actually being read?

The goal here is to maximize the time that useful rollback is kept available by finding queries generating lots of rollback that isn't actually being read, and isolate that rollback in a separate rollback segment.

-- 
greg