Should 'count' depend on date-modified rather than date-created?

[tim-in-oz]

Because my stats are messed up by the fact that i CREATED some
pomodoros on one day, intending to complete them on another.
So the system says they were estimated for THAT day.

Also, it would be good to have a way to be able to create and estimate
pomodoros to do a couple of days in the future, and as it currently
stands, this is not possible without causing probs with the stats.

For example, let's say today you create a pomodoro without entering an
estimate. You just put the estimate in brackets next to the name of
your pomodoro, to do later. It will appear in grey and have no stats.
This is a good way to create a pomodoro to do say, tomorrow or the
next day.
Then tomorrow comes. You 'activate' that p by writing in an estimate.
However, it will appear in the stats for YESTERDAY.

If the stats for p's were done according to the day they were MODIFIED
(rather than created), then:
- you could create tasks and estimates for tomorrow and the next day
(i know you don't want TOO many, but ones for the next day are good)
- you would not get the problem of wrong estimates