To clarify, I actually work for Microsoft as a consultant and asked the question of the wake-up internally before I posted the question in this forum. I don't know if you are able to see my email address in my profile, but if you would like to verify, my address is michael dot waterman at Microsoft dot com.
My apologies; you are the one-in-a-million exception to the rule. When someone is on their first post to the D-Link forum and has an issue with Windows 7, let alone a build that's not officially released, my ass-u-me gear goes into full effect.

What I'd really like to know is the rationale behind waking up to an ARP request. Let me start by saying I'm by no means a network engineer - after reading that article I can think of cases where applications used at my workplace would constantly wake up Vista PCs: Dell OpenManage (packet directly addressed to a mac & NETBIOS addressing), VMWare vSwitches (ARP packets), Intel AMT/SOL (mac packets/ipv6 discovery) to name a few. One of the few (possibly incorrect) scenarios I can think of is the "always connected" theme of Vista where a PC acting as a media server say Vista Home Premium/Ultimate with Media Center in use would go to sleep, but a TV or another PC attempts to open a shared media file while the media center is sleeping, this mechanism would wake up that PC.
WOL isn't used at my workplace, and even if I did, I would prefer the OS only respond to Magic Packets. Of course the article you linked addresses that issue nicely.

What I'd really like to see, Michael, is a Wireshark capture of only your Vista machine attached to 655, and observe/highlight the packet data that causes it to wake:
Linux Wireshark Capturing Computer -----|
Hub<--->DIR-655
Windows Vista Machine -----------------|
Food for thought.