Excel 2010 Recalculation Bug

Recalculation not working in Excel 2010, but does it in 2003. . .

In a blank workbook in a blank worksheeet . . .

Cell A1 is "=MAX(A4:A5)"
Cell A2 is "=A1"
Cells A3:A5 is an Excel Table (created from Insert tab, Tables group, Table)
Cell A3 is "Nbr"
Cell A4 is "1"
Cell A5 is "2"

1 Review formulas in cells A1 & A2
2 Enter a "3" into cell A6
3 Again, review formulas in cells A1 & A2
4 Observe values in cells A1 & A2
5 Note that A1 ≠ A2

It does on my computer

OK - agreed a bug . . .

I have found 2 work-arounds . . .
1. change formula in Cell A1 to "=MAX(Table1[Nbr])"
2. change formula in cell A2 to "=A1+NOW()-NOW()

Either one works but I have hundreds of old Excel 2003 files that will need thousands of formulas to be changed.

How do I report this Excel 2010 recalculation bug to Microsoft?
In Excel 2010, in a blank workbook in a blank worksheet , make the following entries – all entries are made without the quotation marks . . .

In Cell A3 enter the text “Number”
In Cell A4 enter the numeral “1”
In Cell A5 enter the numeral “2”

Select the 3 cells, Cells A3, A4 and A5
Create an Excel Table using Cells A3:A5
(Ribbon, Insert tab, Tables group, Table - - - check mark in the check box to indicate that the Table has headers)

In Cell A1 enter the formula “=MAX(A4:A5)”
In Cell A2 enter the formula “=A1”
In Cell A6 enter the numeral “3”
*** Note the error in Cell A2.
Cell A2 fails to recalculate and it does not equal the new value calculated in Cell A1.

Well after countless hours of searching, I could not find a direct website where I could submit to Microsoft the bug that exists in Excel 2010 and 2013. So I called 1-800-936-5800 and spoke with a customer service rep. She informed me that if I open a "case" with tech support, I would not be charged any money if the tech support rep determined that the problem is an actual "bug". So being the gambler that I am, I rolled the dice, and provided her with my credit card number. She processed a "pre-authorized fee" of $259, opened a case, and provided me with the case number. Less than 1 hour later, I was contacted by a tech support engineer, and in less than 5 minutes he was able to re-create the problem. Then he excused himself from the phone call saying that he needed to do some checking. One hour later he called back and relayed the following . . . He took the situation to his peers, who were also able to re-create the problem. Then he took the situation to the highest ranking senior tech support engineer, and that person confirmed that it is a bug. So I do not have to pay the $259 and the bug is now officially reported to Microsoft by me. So what remains to be seen is how soon the problem is remedied.

My opinion is that Microsoft should have better methods for reporting bugs.