It's been a while now so I take it this module idea has been dropped. If you have any code it would be helpful to others if we could see it.

I'm in a similar situation as many others here, I'm setting up a website for a theater and they want to allow tickets for shows with certain dates. All that's required on the front-end is a drop-down list of available dates. A date attribute does sound like the obvious answer.
However, I guess where it becomes tricky is the current setup of the attribute module gets you to insert each option manually.
The way I see it, it should be more like a date cck field (that you could set to have unlimited values in cck). And each new date added would become an attribute.

Thinking of it like like this (using a cck field), makes me think it could be done simply by node types....
So you'd create an event, which itself wouldn't be a product. But you would then have a 'date' node type, that is a product. This would just have one field (a date cck) field, which you could associate to the event node using node reference. There are many modules that allow the creation/editing of reference nodes quite easily (node relationships is one that comes to mind). You could also use the auto node title module to give the date node type the name of the event (with perhaps the date added on).

Then using views you could display the dates with the event all in one. Might need a bit of coding for the order selection and add to cart button. But I don't think it would be too much. An essentially you would have each date as it's own product with a separate SKU and stock levels.

Another alternative could be using the uc_node_checkout module, which I have yet to explore. But from what I understand it would involve creating a content type for each event, which does not seem suitable (as all my events will have the same fields). I also can't see how it could manage stock levels for dates.

Any thoughts from anyone on my solution (using a "date" node type and referencing the event)?