I don't believe you need to worry. You should always write secure code, and validate and sanitise your data before doing anything with it anyways. I.E: don't assume id=xxx is valid, as someone could manually type something knowing the script URL.
Most of the sites you see are probably using a framework or some sort of url rewriting. This makes the URL's look nicer (even scripts). It doesn't add much in the way of security though, this could be considered Security through Obscurity. It would do nothing more than prevent someone who doesn't know what they are doing from an easy attack. It would never stop a skilled attacker, and this is why security should be implemented on the server side.
Edit:
As a side note, you may want to use POST for delete just to prevent some nasty unforseen consequences. As Tim said, you should have a delete confirmation page, cause even if the user is logged in, it doesn't mean they are in control.
Imagine a website with an iframe set to width=0 and height=0 src=http://yoursite.com/php/delete.php?id=xxx
This would cause the logged in user to delete their account. (Or change password, charge credit card, etc) without their knowledge.
Of course changing GET to POST doesn't completely resolve this issues, but its one step of many to take in securing web apps.