Yeah, apparently the server techs were overly optimistic about their efforts. My programmer pretty much has proven the insertion of malicious code is at the Apache level on the server, but he'd having a tough time convincing the server techs of it. So I've contracted with a third party server security outfit to take a look at it. Just as soon as I can get the current server techs the heck out of the server so I don't have too many people stirring the pot on this stew.
Interestingly enough part of the proof my programmer found as evidence is the reason that I was seeing these redirects on my CorvetteFlorida.com website. I have a link over there from my FaunaAds.com advertising script and apparently when viewers on that site were supposed to be presented with a banner image, the malicious script instead inserted a redirect to the porn site. When he removed the banner ad link, the problem stopped over there. So that's why he believes the insertion is at the Apache level. He was monitoring the handshaking of commands, and it's Apache that is doing the sleight of hand by issuing a redirect to another site instead of a direct issuance of the desired page or page element.
Yeah, he's pretty damned good at what he does. But we still need someone with expertise beyond his to really ferret out the problem.
So it should be SOON. Thanks for your patience as we deal with this.