如果在调试模式下编译软件，许多编译器将不会内联vector的访问器函数。这将使stl向量的实现在性能有问题的情况下变得更慢。它还将使代码更容易调试，因为您可以在调试器中看到分配了多少内存。

在优化模式下，我希望stl向量接近数组的效率。这是因为许多vector方法现在都内联了。

There is no argument about which of them is the best or good to use.They both have there own use cases,they both have their pros and cons.The behavior of both containers are different in different places.One of the main difficulty with arrays is that they are fixed in size if once they are defined or initialized then you can not change values and on the other side vectors are flexible, you can change vectors value whenever you want it's not fixed in size like arrays,because array has static memory allocation and vector has dynamic memory or heap memory allocation(we can push and pop elements into/from vector) and the creator of c++ Bjarne Stroustrup said that vectors are flexible to use more than arrays.

应该避免使用带有new的c++数组(即使用动态数组)。有一个问题是，你必须跟踪它们的大小，你需要手动删除它们，并做所有的家务工作。

我们还可以很容易地在向量中插入、推入和拉出值，这在数组中是不容易做到的。

如果我们讨论性能，那么如果你处理小的值，那么你应该使用数组，如果你处理大规模的代码，那么你应该使用向量(向量比数组更擅长处理大的值)。

选择STL。没有性能损失。这些算法非常高效，它们在处理我们大多数人不会想到的细节方面做得很好。

STL is a heavily optimized library. In fact, it's even suggested to use STL in games where high performance might be needed. Arrays are too error prone to be used in day to day tasks. Today's compilers are also very smart and can really produce excellent code with STL. If you know what you are doing, STL can usually provide the necessary performance. For example by initializing vectors to required size (if you know from start), you can basically achieve the array performance. However, there might be cases where you still need arrays. When interfacing with low level code (i.e. assembly) or old libraries that require arrays, you might not be able to use vectors.

如果在调试模式下编译软件，许多编译器将不会内联vector的访问器函数。这将使stl向量的实现在性能有问题的情况下变得更慢。它还将使代码更容易调试，因为您可以在调试器中看到分配了多少内存。

在优化模式下，我希望stl向量接近数组的效率。这是因为许多vector方法现在都内联了。

我认为最主要的问题不是性能，而是安全性。使用数组可能会犯很多错误(例如，考虑调整大小)，而使用向量可以省去很多麻烦。