Note that companies controlling both the devices/apps and the store (e.g., Amazon or Kobo) perform analytics routinely, exactly because they can gather info from the reading system (app or device firmware). They even share their findings with the publishers (to make them "optimize" their eBooks, so that they can sell more)
EDIT: see "/data lessons/", presentation by Tamblyn (Kobo) given at BiB12: http://youtu.be/eQfJ3NWiPmU
Some guys tried to build a company (Hiptype) around the concept of "google analytics" for eBooks, but they did not succeed and went out of money. Their solution was basically embedding JS code into EPUB eBooks. This type of solution is quite doomed, because if the reading system disallows network communication (e.g., iBooks does), the ebook cannot "phone home" the reading statistics. The same holds true for remotely-hosted images (like those used to log the visitors of a web page).
Finally, no ebook standard that I am aware of has explicit mechanisms to collect such statistics. And, even if they had, the actual availability of such a feature would be depending on the reading system implementer.