Ping -i Command

I like this command.  Its been helpful to me because when I need to do a traceroute and the firewall guys at a customer site decide they want to block that, well, that just wont do.  So, Ill go at it another way.  I use the 'ping -i' command.
So notice below that every time I do a ping, I increase the hop by one.  First, I do 3, then 4, then 5.  Notice that the replying IP address is different every time.  


C:\Users\skillen>ping -i 3 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
Reply from 96.34.74.140: TTL expired in transit.
Reply from 96.34.74.140: TTL expired in transit.
Reply from 96.34.74.140: TTL expired in transit.
Reply from 96.34.74.140: TTL expired in transit.

Ping statistics for 4.2.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\skillen>ping -i 4 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
Reply from 96.34.79.22: TTL expired in transit.
Reply from 96.34.79.22: TTL expired in transit.
Reply from 96.34.79.22: TTL expired in transit.
Reply from 96.34.79.22: TTL expired in transit.

Ping statistics for 4.2.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\skillen>ping -i 5 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
Reply from 96.34.74.241: TTL expired in transit.
Reply from 96.34.74.241: TTL expired in transit.
Reply from 96.34.74.241: TTL expired in transit.
Reply from 96.34.74.241: TTL expired in transit.

Ping statistics for 4.2.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Notice this traceroute chart, and you will see that the above is reflected correctly.