Changing some of the wording in the suggestions area is a good idea. I did not realize there was so much general confusion about it!
I'd like to say again that sometimes a particular suggestion that is very popular has not yet been implemented due to the technical complexity of the implementation and not because we are deciding to not do it at all. That is true for 3 out of the top 6 voted suggestions at the moment. Other suggestions that may get fewer votes are implemented sooner because they are simple or quick to implement.
The phpmyadmin upgrade is currently the 15th most voted on suggestion. However, I believe we are currently working on it and it should be rolled out in the next week or two. We make some of our own modifications to the source to suit our needs so it takes a little longer than a simple upgrade would normally. This is not an official announcement of it but I heard some rumbling about it the other day. Please don't hold us to it!
The Awstats suggestion (the suggestion says to completely replace Analog with it) is currently the 12th most voted on suggestion. I have been personally using Awstats for a couple of sites hosted by us (including dreamhost.com) for a few months now to get a feel for how well it works and how much server resources it uses up. I can say it is very likely that we will offer Awstats or another stats program as an additional alternative to Analog at some point this year. It is unlikely that we would start running it on all domains all at once as we would not replace Analog with it. I have been using Awatsts for my own website and I do find the reports more visually appealing than Analog's, but I still find myself turning back to Analog for specific information I have become accustomed to. They each provide different information in different ways.
There are also technical reasons why we stick with Analog as our default stats mechanism, the main one being the amount of cpu resources it takes to generate reports. Based on information I have seen Analog is around 9 times faster than any other program out there. When you're running it on over 100,000 domains 3 times a day (once for each report we keep) that adds up fast! However, if the stats are not providing our customer base with information they find to be valuable that may not be so important.
You should note that it is quite easy to set up Awstats on a domain yourself. It does take a little know-how to set up the cron job, Awstats itself is easy to configure. We like to leave our system flexible for anyone who wants to take things into their own hands. I have been meaning to write some documentation about how to set up and configure the most common web stats tools on our servers for anyone interested in doing that, but other things have kept me too busy to do so.