Type of array/vector incorrect in IntelliSense after a typedef and another array/vector

Bug type: Language Service

Describe the bug

• OS and Version: Windows 11 Pro
• VS Code Version: 1.57.1
• C/C++ Extension Version: 1.5.0-insiders3
  In some cases the type of the elements of an array/vector is incorrect in IntelliSense after a typedef and another array/vector.

Steps to reproduce

1. Paste the following code into a cpp file:

#include <vector>

typedef int my_type;
std::vector<my_type> v;

void f(std::vector<int> x) {}

2. Hover over the f (or x).
3. The tooltip says x is a std::vector<my_type>.
4. Notice how under Outline it is displayed as std::vector<float>.

Expected behavior
x should be a std::vector<float>.

A more general way to reproduce this is:

1. Define a new type: typedef <existing_type> <new_type>;
2. Define an array/vector of <new_type>.
3. Define a function/variable that is/has an array/vector of <existing_type>.
4. IntelliSense will tell it is an array/vector of <new_type>.

Screenshots

Additional context
Visual Studio 2019 seems to have the same issue.

Start with the C++ language service IntelliSense handling for typedefs and std::vector or array types, using the reproduction snippet in the issue. Verify the hover tooltip and Outline display for the function parameter, and consider the bug done when both report the correct element type without being affected by the preceding typedef and vector.