Events in the Same DB Table as Groups?

It appears that ES 1.3 is storing both groups and events in the same database table (_social_clusters). I understand that they use pretty much the same data structure. However I recall the stacked team specifically uses more tables to optimize speed (great on you guys, perhaps maintain this practice for events/groups). So I'll highlight some concerns with the current method:

• Up to double the records in a single table, possible speed loss.
  


• ID numbers will increase faster and will not give users an accurate representation of the object count for that type of object.
  


• Alias's are stored under the same table. As a result you could not have /group/test and event/test as the main alias name at the same time. The auto incrementing set in place helps the situation, but makes one have to deal with more numbers. Separation of the db table would allow for them both to qualify as unique without the auto increment having to take place.
  

Considering that events is not yet on public sites, it's not too late to change if there are better practices. I'm not saying I'm right here, I'm bringing in food for thought to think/talk about.