>I can see how, if it were implemented as a simple list, things could get out of hand.
>
>It'd have to have verification and voting features for each item, with an ability for the community to 'strike' a report if it were collectively deemed to be frivolous. Discussion threads and code samples would have to be enabled for each item

I don't think there is any need to make it so formal. We are already able to post a message here on the UT about what we think is a bug. Having a list in one handy place here on the UT, rather than scattered across many posts, is just convienient. If people want to attach there comments about each possible bug, including comments such as:

That they can't reproduce it
Why they don't think it's a bug
How to work around it

That would be great. But I don't think having a formal verification and voting procedure would cause more troubles than it would fix.