A lot of CCIE's including myself have adopted a common practice of re-using the same hsrp group # on multiple vlans.
It simplifies configuration, administration, troubleshooting, etc. plus on various platforms you may be limited to as few as 16 groups or 256, neither of which proves sufficient depending on how many vlans you have in a given environment so whats the point of naming a unique hsrp group after the vlan # when it won't scale anyway and isn't needed?
http://www.cisco.com/warp/public/473/168.html#q1
Q. What is the implication of using the same HSRP group ID on multiple interfaces?
A. When you define the same HSRP group ID on multiple interfaces, they share the same HSRP virtual MAC address. In most modern LAN switches, there are no issues because they maintain a per-VLAN MAC address table. However, if your network contains any third-party switches, which maintain a system wide MAC address table regardless of VLAN, you can experience problems.
Other advice I'd give you is:
-do use hsrp authentication
-do set the primary hsrp with a higher priority
-do set the primary hsrp with preempt
-do consider glbp (gateway load balancing protocol) instead of hsrp if you need outbound load balancing on your first hop; return traffic is normally load balanced via your dynamic routing protocols
-do use igmp/cgmp since hsrp is multicast
-don't mess with hsrp timers (as a general rule)
Enjoy.
