Yes! If you read my posts from last night, you will see that it HAD to be planted. It was a static file AND it was a .bmp file. Google Maps does not have .bmp files for searches. The cursor files are .cur. They had to get to this in a roundabout way, but there is no doubt.
The best way to see all this is to clear your own cache and do a simple Google search via your zip code. Zoom in two ways and compare your files.
For the first means, type in your zip code and then zoom in with the buttons provided on the side of the Google tool.
Compare your cache, then empty it again.
Next, type in your zip code, but only zoom in by selecting the small arrow on the lower right of the Google map. A zoom in field will show up that allows you to zoom with your mouse.
Compare the files in your cache.
When I did this last week, I got an open hand cursor file and a closed hand cursor file document in my cache.
The name Google assigns the file has a .cur at the end.
Windows associates this file since it doesn't have a program to read this file as a .bmp file.
I couldn't get this file to open, but it did allow me to see the differences of the files and how they are associated in Windows.
If having a .cur file that Windows identifies as a .bmp file means a computer has been compromised and files have been planted, then that's what I did to myself last week when I tried the process out myself.
If I had time, I'd do a demo.
I'm not a computer professional and this is just something I noticed on my own when the "bombshell" testimony came out last week at the end of the pros case.
It is something that, from what I can see, is natural to a computer using Google and doesn't indicate, at least to me from my playing on my computer, proof that a file is planted.